iFTP HISTORY FILE
-----------------

2.1    - Official release

2.1a   - Added RENAME Script command.

         RENAME <oldfilename> <newfilename>

         Remame old file name to new file name.

         Usage Notes:

         Both files must be on the same machine.

         When using DOS files, the new file name can be on a different
         directory or dos drive.  So effectively, you can use this as a
         move operation with the ability to rename the file at the same
         time. For example:

                rename c:\file1.txt d:\backup\file3.txt

         When working with remote files on a FTP server, there might be
         some FTP servers who may or not honor the concept of moving a
         file when using the rename command.  Be aware that some FTP
         servers, may not allow operation. For example:

                 rename /file1.txt /textfiles/file20.txt

         The above command may work for some servers, not all.

       - The MOVE command:

                MOVE <RemoteSourcefile> <RemoteTargetPath>

         Is now an acceptable command format when the source file(s) and
         target path are are on the same remote machine.  You can use
         this command to move a set of files from one directory to
         another.  For example:

                      move /*.zip  /zipfiles

         The above command will move the remote *.zip in the root
         directory to the /zipfile directory.  The directory must
         already exist.

2.1b   - iFTP now dynamically checks for RAS.  This means that RAS does
         not have to be installed on the machine in order to use iFTP.
         This is meant for using iFTP to connect to FTP servers on the
         LAN or WAN.

2.1c   - Fixes problem w/ dynamic loading of RAS in 2.1b.

06/29/98 07:16 am

2.1d   - New PROXY section in INI file.  This will allow for greater
         control over proxy setups.  See the INI file for details.

       - The SaveDate Option and the script command Update will assume
         the remote file date is a "local File Date" and not System or
         GMT date.  If you know the remote file server displays GMT
         dates, then use the new option UseGMTDate to retain the
         original iFTP date behavior.  What this means is that the
         remote file date will be used as the local storage file date
         when downloading the file.  Previous iFTP would apply your
         international GMT bias offset to the date.

       - New global environment strings:

            %date%      current date in MM/DD/YYYY format, i.e, 06/28/1998
            %time%      current time in HH:MM:SS format, i.e, 18:24:00
            %day%       current day (abbreviation), i.e, Mon, Wed, Sat..

       - New IF TIMERANGE command.

         Example, this will test that the current time is within the
         begin and end time (in HH:MM:SS format):

            if timerange <begintime> <endtime> .....